Unlike many of our competitors, Spira does not include formal rate-limiting mechanisms for API calls. This allows our customers to use Spira at maximum scale. In addition, with the increasing use of MCP to integrate Spira into agentic workflows, more of the workloads accessing Spira will be API vs. UI. However, when you make lots of API calls in parallel, there may be cases where updating certain data items will block reading those same items due to database row-locking. This KB articles provides some best practices for designing your API strategy when using Spira for maximum performance.
If you use SpiraTeam, SpiraTest, or SpiraPlan integrated with Jira Cloud, you need to be aware of a recent change in Atlassian’s platform policy around API rate limiting.